docs: Promote the usage of LazyLock instead of lazy_static #550
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Welcome @Expyron! It looks like this is your first PR to tikv/rust-prometheus 🎉 |
Signed-off-by: Expyron <[email protected]>
Contributor
|
#556 does this plus remove the dependency on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Rust 1.80, the recommended way to have lazily-initialized statics is to use
LazyLock.As this crate's MSRV is 1.81, this PR updates the documentation to encourage that new usage.
This is a change to examples and documentation only.
Once this PR is merged, I'll make another PR updating the internal uses of
lazy_staticwithin this crate.